Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump @opentelemetry/semantic-conventions from 1.25.1 to 1.26.0 in the otel group #427

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 26, 2024

Bumps the otel group with 1 update: @opentelemetry/semantic-conventions.

Updates @opentelemetry/semantic-conventions from 1.25.1 to 1.26.0

Release notes

Sourced from @​opentelemetry/semantic-conventions's releases.

semconv/v1.26.0

@opentelemetry/[email protected]

Note: This package will now be versioned according to the version of semantic conventions being provided.

🚀 (Enhancement)

  • feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
    • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
    • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Changelog

Sourced from @​opentelemetry/semantic-conventions's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG.

Unreleased

💥 Breaking Change

🚀 (Enhancement)

  • feat: include instrumentation scope info in console span and log record exporters #4848 @​blumamir
  • feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @​dyladan
    • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
    • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
    • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

🐛 (Bug Fix)

  • fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @​trentm
  • deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @​lforst
  • fix(instrumentation): Fix optional property types #4833 @​alecmev
  • fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

📚 (Refine Doc)

🏠 (Internal)

  • refactor: Simplify the code for the getEnv function #4799 @​danstarns
  • refactor: remove "export *" in favor of explicit named exports #4880 @​robbkidd
    • Packages updated:
      • opentelemetry-context-zone
      • opentelemetry-core
      • opentelemetry-exporter-jaeger
      • opentelemetry-exporter-zipkin
      • opentelemetry-propagator-b3
      • opentelemetry-propagator-jaeger
      • opentelemetry-sdk-trace-base
      • opentelemetry-sdk-trace-node
      • opentelemetry-sdk-trace-web
      • propagator-aws-xray
      • sdk-metrics
  • deps(sdk-metrics): remove unused lodash.merge dependency #4905 @​pichlermarc
Commits
  • 3cf1c52 chore: prepare next release (#4939)
  • 5578a11 chore: sync package-lock.json (#4947)
  • 5c1ae0a docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...
  • 0b8d310 fix(sdk-metrics): use inclusive upper bounds in histogram (#4935)
  • 0ee398d fix(instrumentation): ensure .setConfig() results in config.enabled defaultin...
  • 7aff06d chore(release): script to align workspace on new semconv package version (#4937)
  • f2a6bcc feat(otlp-exporter-base)!: use transport interface in web exporters (#4895)
  • cd4e2bf fix(otlp-exporter-base): fix handling of destroyed requests (#4929)
  • 583154c chore(semconv): Separate SemConv releases to allow different versioning (#4904)
  • 14d086a feat(sdk-node)!: Automatically configure logs exporter (#4740)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the otel group with 1 update: [@opentelemetry/semantic-conventions](https://github.com/open-telemetry/opentelemetry-js).


Updates `@opentelemetry/semantic-conventions` from 1.25.1 to 1.26.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v1.25.1...semconv/v1.26.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/semantic-conventions"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: otel
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner August 26, 2024 13:40
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 26, 2024
@raphael-theriault-swi
Copy link
Member

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 28, 2024

Looks like @opentelemetry/semantic-conventions is updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Aug 28, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/otel-f38a61f06e branch August 28, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Development

Successfully merging this pull request may close these issues.

1 participant